Systems and methods for creating multi-applicant account

ABSTRACT

Methods and systems for creating a multi-applicant account profile are described. During a first remote session, a first applicant provides at least two pieces of contact data for second applicant. A unique link and a one-time password are transmitted to the second applicant using respective first and second pieces of contact data. A second remote session is initiated, in response to receipt of the one-time password, provided via the unique link. During the second remote session, identification information of the second applicant is provided. A new multi-applicant account profile is then created, after verifying the identification information of the first applicant and the second applicant.

FIELD

The present disclosure is related to systems and methods for creating amulti-applicant account.

BACKGROUND

In order to conduct transactions with a customer, an institution maycreate an account profile for that customer. The account profile may belinked with a profile of the customer, for example. In some examples, anaccount profile may be linked with profiles of two or more customers.For example, in the case of a financial institution, a joint account(also referred to as a multi-applicant account) may be created andlinked to two or more customer profiles.

Typically, creating a new multi-applicant profile account requiresverification of the identification of all applicants. In some examples,such as institutions that require an in-person visit to create a newaccount profile, this may require all applicants to be physically at thesame location at the same time. This requirement may be inconvenient.

Some institutions enable creation of a new account profile by anapplicant via an online session. However, this is typically limited tosingle applicant accounts; or typically requires all applicants of amulti-applicant account to provide identification information during thesame online session. Again, this could be inconvenient or difficult tocoordinate, especially when there are many applicants. Further, therecould be privacy issues in sharing an online session among multipleapplicants. For example, each applicant may have access to theidentification information of each other applicant.

Accordingly, there is a need for improved methods, devices and systemsrelated to creation of a multi-applicant account profile.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example, to the accompanyingdrawings which show example embodiments of the present application, andin which:

FIG. 1 is a schematic diagram of an example network environment in whichexample embodiments of the present disclosure may be implemented;

FIG. 2 is a block diagram of a web application server in accordance withexample embodiments of the present disclosure;

FIG. 3 is a block diagram of an example client device that may be usedwith example embodiments of the present disclosure;

FIG. 4 is a signaling diagram illustrating an example method forcreating a multi-applicant account profile;

FIG. 5 is a flowchart illustrating an example method performed by theapplication server, as part of the method of FIG. 4 ;

FIGS. 6A-6E show example user interfaces that may be displayed duringthe method of FIG. 4 ;

FIG. 7 is a signaling diagram illustrating another example method forcreating a multi-applicant account profile;

FIG. 8 is a flowchart illustrating an example method performed by theapplication server, as part of the method of FIG. 7 ; and

FIGS. 9A-9C show example user interfaces that may be displayed duringthe method of FIG. 7 .

Similar reference numerals may have been used in different figures todenote similar components.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The present disclosure is made with reference to the accompanyingdrawings, in which embodiments are shown. However, many differentembodiments may be used, and thus the description should not beconstrued as limited to the embodiments set forth herein. Rather, theseembodiments are provided so that this disclosure will be thorough andcomplete. Like numbers refer to like elements throughout. Separate boxesor illustrated separation of functional elements of illustrated systemsand devices does not necessarily require physical separation of suchfunctions, as communication between such elements may occur by way ofmessaging, function calls, shared memory space, and so on, without anysuch physical separation. As such, functions need not be implemented inphysically or logically separated platforms, although they areillustrated separately for ease of explanation herein. Different devicesmay have different designs, such that although some devices implementsome functions in fixed function hardware, other devices may implementsuch functions in a programmable processor with code obtained from amachine-readable medium. Elements referred to in the singular may beimplemented in the plural and vice versa, except where indicatedotherwise either explicitly or inherently by context.

In accordance with one aspect of the present disclosure, there isprovided a server, which may be an application server. The serverincludes at least one communication interface for communication with oneor more client devices. The server also includes a processor coupled tothe communication interface and a memory coupled to the processor. Thememory includes computer-executable instructions stored thereon. Theinstructions, when executed by the processor, cause the server to,during a first remote session, receive, via the communication interface,a signal representing identification information of a first applicant,and a signal representing at least two pieces of contact data for secondapplicant. The instructions also cause the server to transmit, using afirst piece of contact data for the second applicant, via thecommunication interface, a signal representing a unique link. Theinstructions also cause the server to transmit, using a second piece ofcontact data for the second applicant, via the communication interface,a signal representing a one-time password. The instructions also causethe server to initiate a second remote session, in response to receipt,via the communication interface, of a signal representing the one-timepassword, the one-time password being provided via the unique link. Theinstructions also cause the server to, during the second remote session,receive, via the communication interface, a signal representingidentification information of the second applicant. The instructionsalso cause the server to create a new multi-applicant account profile,after verifying the identification information of the first applicantand the identification information of the second applicant.

In accordance with another aspect of the present disclosure, there isprovided a method at a server, such as an application server. The methodincludes, during a first remote session, receiving a signal representingidentification information of a first applicant, and a signalrepresenting at least two pieces of contact data for second applicant.The method also includes transmitting, using a first piece of contactdata for the second applicant a signal representing a unique link. Themethod also includes transmitting, using a second piece of contact datafor the second applicant, via the communication interface, a signalrepresenting a one-time password. The method also includes initiating asecond remote session, in response to receipt of a signal representingthe one-time password, the one-time password being provided via theunique link. The method also includes, during the second remote session,receiving a signal representing identification information of the secondapplicant. The method also includes creating a new multi-applicantaccount profile, after verifying the identification information of thefirst applicant and the identification information of the secondapplicant.

In accordance with another aspect of the present disclosure, there isprovided a non-transitory machine-readable medium having tangibly storedthereon executable instructions for execution by a processor of aserver, such as an application server. The instructions, when executedby the processor, cause the server to, during a first remote session,receive, via the communication interface, a signal representingidentification information of a first applicant, and a signalrepresenting at least two pieces of contact data for second applicant.The instructions also cause the server to transmit, using a first pieceof contact data for the second applicant, via the communicationinterface, a signal representing a unique link. The instructions alsocause the server to transmit, using a second piece of contact data forthe second applicant, via the communication interface, a signalrepresenting a one-time password. The instructions also cause the serverto initiate a second remote session, in response to receipt, via thecommunication interface, of a signal representing the one-time password,the one-time password being provided via the unique link. Theinstructions also cause the server to, during the second remote session,receive, via the communication interface, a signal representingidentification information of the second applicant. The instructionsalso cause the server to create a new multi-applicant account profile,after verifying the identification information of the first applicantand the identification information of the second applicant.

In any of the above, the server may further: during the first remotesession, receive, via the communication interface, a signal representingat least two pieces of contact data for a third applicant; transmit,using a first piece of contact data for the third applicant, via thecommunication interface, a signal representing another unique link;transmit, using a second piece of contact data for the third applicant,via the communication interface, a signal representing another one-timepassword; initiate a third remote session, in response to receipt, viathe communication interface, of a signal representing the other one-timepassword, the other one-time password being provided via the otherunique link; and during the third remote session, receive, via thecommunication interface, a signal representing identificationinformation of the third applicant. The new multi-applicant accountprofile may be created after verifying the identification information ofthe first applicant, the identification information of the secondapplicant, and the identification information of the third applicant.

In any of the above, the second remote session and the third remotesession may be conducted in parallel, or in any temporal order.

In any of the above, the server may further: during the second remotesession, receive, via the communication interface, a signal representingat least two pieces of contact data for a third applicant; transmit,using a first piece of contact data for the third applicant, via thecommunication interface, a signal representing another unique link;transmit, using a second piece of contact data for the third applicant,via the communication interface, a signal representing another one-timepassword; initiate a third remote session, in response to receipt, viathe communication interface, of a signal representing the other one-timepassword, the other one-time password being provided via the otherunique link; and during the third remote session, receive, via thecommunication interface, a signal representing identificationinformation of the third applicant. The new multi-applicant accountprofile may be created after verifying the identification information ofthe first applicant, the identification information of the secondapplicant, and the identification information of the third applicant.

In any of the above, the server may further: transmit, via thecommunication interface, signals representing a notification to thefirst applicant indicating addition of the third applicant. The newmulti-applicant account profile may be created after receiving, via thecommunication interface, signals representing confirmation of the thirdapplicant by the first applicant.

In any of the above, the at least two pieces of contact data for thesecond applicant may include at least two of: an email address; a phonenumber; or a social media account.

In any of the above, the signal representing the unique link may betransmitted using one of: an email message to the email address; a textmessage to the phone number; or a private message to the social mediaaccount. Further, the signal representing the one-time password may betransmitted using a different one of: an email message to the emailaddress; a text message to the phone number; or a private message to thesocial media account.

In any of the above, the server may receive the identificationinformation from one of the first applicant or the second applicant by:verifying that the one of the first applicant or the second applicant isan existing customer; and retrieving the identification information ofthe one of the first applicant or the second applicant from a customerdatabase.

In any of the above, the server may further: after creating themulti-applicant account, transmit, via the communication interface,signals representing a respective notification to each applicant toindicate the multi-applicant account was successfully created.

In any of the above, the identification information of the secondapplicant may be inaccessible to the first applicant, and theidentification information of the first applicant may be inaccessible tothe second applicant.

FIG. 1 shows an example network 100 which may be used to implementexamples described herein. In this example, a plurality of clientdevices 110 a-110 n (generally referred to as client device(s) 110) maybe connected, through a communication network 120, to an applicationserver 200 via any suitable communications links, such as network links,wireless links, hard-wired links, and the like. The client devices 110a-110 n may be the same or different from each other. For example, eachclient device 110 may be an instance of the example client device 110illustrated in FIG. 3 and described further below.

Examples of the client device 110 include, but are not limited to,handheld or mobile wireless communication devices, such as personaldigital assistants (PDAs), smartphones, tablets, laptop or notebookcomputers, netbook or ultrabook computers; as well as vehicles having anembedded-wireless communication system, such as a Wi-Fi or cellularequipped in-dash infotainment system, or tethered to another wirelesscommunication device having such capabilities. Examples of the clientdevice 110 may also include sensors or other wirelessly connecteddevices, such as internet of things (IoT) devices or smart speakers,among other possibilities. Mobile wireless communication devices mayinclude devices equipped for cellular communication through PLMN orPSTN, mobile devices equipped for Wi-Fi communication over WLAN or WAN,or dual-mode devices capable of both cellular and Wi-Fi communication.In addition to cellular and Wi-Fi communication, a mobile wirelesscommunication device may also be equipped for Bluetooth and/or NFCcommunication. In various embodiments, the mobile wireless communicationdevice may be configured to operate in compliance with any one or acombination of a number of wireless protocols, including Global Systemfor Mobile communications (GSM), General Packet Radio Service (GPRS),code-division multiple access (CDMA), Enhanced Data GSM Environment(EDGE), Universal Mobile Telecommunications System (UMTS),Evolution-Data Optimized (EvDO), High Speed Packet Access (HSPA), 3rdGeneration Partnership Project (3GPP), or a variety of others. It willbe appreciated that the mobile wireless communication device may roamwithin and across PLMNs. In some instances, the mobile wirelesscommunication device may be configured to facilitate roaming betweenPLMNs and WLANs or WANs.

The communication network 120 may include any one or more suitablecomputer networks including, for example, the Internet, an intranet, awide-area network (WAN), a wireless WAN (WWAN), a local-area network(LAN), a wireless LAN (WLAN), a wireless network, a digital subscriberline (DSL) network, a frame relay network, an asynchronous transfer modenetwork, a virtual private network (VPN), a public-switched telephonenetwork (PSTN), or a public-land mobile network (PLMN), or anycombination of any of the same. Network communications may befacilitated through the use of any suitable communication such astransmission control protocol/internet protocol (TCP/IP), Ethernet, filetransfer protocol (FTP), hypertext transfer protocol (HTTP), HTTP secure(HTTPS), and the like.

The application server 200 is operable to communicate signals andexchange data with each client device 110, via the communication network120. The application server 200 in this example network 100 is alsocoupled to an authentication server 130 that is operable to provideauthentication services, and a business services server 140 that isoperable to provide account management services. The application server200, authentication server 130 and business services server 140 may allbe operated by a common operator, such as a financial institution. It isto be appreciated that although one instance each of the applicationserver 200, authentication server 130 and business services server 140are shown, there may be more than one instance of each server 200, 130,140. Further, the functions of the application server 200,authentication server 130 and business services server 140 may beperformed using greater or fewer numbers of servers. For example, theapplication server 200, authentication server 130 and business servicesserver 140 may be replaced by a single server that provides all thefunctions of the application server 200, authentication server 130 andbusiness services server 140. It should be understood that although asingle communication network 120 is shown, there may be multipleinstances of the communication network 120, and the components of thenetwork 100 may communicate with each other via different communicationnetworks 120.

The above-described communication network 100 is provided for thepurpose of illustration only. The above-described communication network100 includes one possible network configuration of a multitude ofpossible configurations. Suitable variations of the communicationnetwork 100 will be understood to a person of skill in the art and areintended to fall within the scope of the present disclosure. In someembodiments, the network includes multiple components distributed amonga plurality of computing devices. One or more components may be in theform of machine-executable instructions embodied in a machine-readablemedium.

Reference is next made to FIG. 2 which illustrates in simplified blockdiagram form details of the application server 200, authenticationserver 130 and business services server 140, in accordance with exampleembodiments of the present disclosure.

The application server 200 includes a controller comprising at least oneprocessor 202 (such as a microprocessor) which controls the overalloperation of the application server 200. The processor 202 is coupled toa plurality of components via a communication bus (not shown) whichprovides a communication path between the components and the processor202. The processor 202 is coupled to a communication interface 204 thatcommunicates directly or indirectly with a corresponding communicationinterface (not shown) of a client device 110, and possibly communicateswith other computing devices by sending and receiving correspondingsignals. The communication interface 204 may communicate via one or acombination of Bluetooth® or other short-range wireless communicationprotocol, Wi-Fi™, and a cellular, among other possibilities. Theprocessor 202 is also coupled to one or more memories 206, which mayinclude one or more of RAM, ROM and/or persistent (non-volatile) memorysuch as flash memory.

The application server 200 may include an optional input/output (I/O)interface 208 for interfacing with optional input devices and/or outputdevices (not shown), such as a keyboard, mouse, touchscreen, displayand/or speaker. The application server 200 may also include various dataI/O ports (not shown) such as serial data port (e.g., USB data port).Operating system software 210 executed by the processor 202 is stored inthe memory(ies) 206, typically the persistent memory but may be storedin other types of memory devices, such as ROM or similar storageelement. Software application(s) 212 executed by the processor 202 mayalso be stored in the memory(ies) 206. System software, softwaremodules, specific device applications, or parts thereof, may betemporarily loaded into a volatile memory, such as RAM, which is usedfor storing runtime data variables and other types of data orinformation. Communication signals received by the application server200 may also be stored in RAM. Although specific functions are describedfor various types of memory, this is merely one example, and a differentassignment of functions to types of memory may be used in otherembodiments.

The processor 202 is coupled to a session manager 220. Although FIG. 2shows the session manager 220 separate from the memory 206, in someexamples the session manager 220 may be implemented using softwareinstructions stored in the memory 206.

The session manager 220 manages sessions between the application server200 and one or more client devices 110. In the present disclosure, asession involves communications (and typically exchange of data) betweenthe application server 200 and a client device 110. Because the user ofthe client device 110 is able to interact with the application server200 of an institution, instead of being physically present at a physicallocation of the institution, such a session may be referred to as aremote session (e.g., in contrast with an in-person session). A form ofremote session is an online session, in which a web-based portal mayprovide access to the application server 200, and in which data may beexchanged via the internet or similar communication network. Other formsof remote sessions may include, for example, a session conducted viatext messages (e.g., using a chatbot or other natural languageprocessing system), or via telephone (e.g., using an interactive voiceresponse system), among other possibilities. For simplicity, unlessexplicitly indicated otherwise, references to a session in the presentdisclosure should be understood to mean a remote session.

A session may be established between a single client device 110 and theapplication server 200, such that the session is specific to that clientdevice 110. The application server 200 may be involved in multiplesessions with multiple different client devices 110 simultaneously. Insome examples, a single client device 110 may be involved in multipledifferent sessions with the application server 200, such as viarespective different applications. The application server 200 mayperform a task or a function (e.g., creating a new customer profile, orcreating a new account profile) that may require two or more sessions(with a single or multiple client devices 110) to complete.

The session manager 220 may store session data 222. Session data 222 mayinclude state information about a current state of an ongoing session,and may also include information about session history. For example,session data 222 may include information that enable two or moresessions to be associated with each other, which may be the case if twoor more sessions are required to complete a task or function.

The application server 200 includes an authorization server applicationprogramming interface (API) 230 and a resource server API 240. Theresource server API 240 is an API that allows the application server 200to communicate securely with a resource server such as the businessservices server 140. The business services server 140 may store data,including private data, which may be exchanged with the client device110. In some examples, the business services server 140 may be operatedby a financial institution such as a bank, and may include an accountdatabase 142 that includes private data in the form of banking data.Data stored in the account database 142 may include account profiles andinformation associated with account profiles. The business servicesserver may also include a customer database 144 that includes customerprofiles containing customer data. Customer profiles in the customerdatabase 144 may be linked to one or more account profiles in theaccount database 142, and vice versa. Account profiles and customerprofiles may also be stored by the business services server 140. In thepresent disclosure, a customer may be a user of the client device 110who has a customer profile and/or who is associated with an accountprofile.

The business services server 140 may also include various functionalmodules for performing operations, such as data queries/searches anddata transfers (e.g., transactions) based upon the banking dataincluding, for example, a transaction module 146 for performing datatransfers/transactions and a transaction analytics module 148 forperforming queries/searches and analytics based on the banking data.

In some examples, authentication of a client device 110 and/or a usermay be required before data exchange with the application server 200 isallowed. In some examples, authentication or verification ofidentification data may be required before a customer profile is createdfor that user (e.g., in the case where the user is not an existingcustomer of the institution), or an account profile is created and/orlinked to that user (e.g., in the case where a customer profile hasalready been created for the user). The specifics of the authorizationand authentication process are outside the scope of the presentdisclosure. The authorization server API 230 is an API that allows theapplication server 200 to communicate securely with the authenticationserver 130 to perform the required authentication or verification. Theauthentication server 130 may be operated by a third-party, and mayfurther communicate with another database and/or server (not shown) toperform the required authentication or verification.

Reference is now made to FIG. 3 , which is a simplified block diagram ofan example electronic device 300. The electronic device 300 may be anexample of a client device 110 that may communicate with the applicationserver 200 as disclosed herein. The electronic device 300 in thisexample includes at least one processing unit 302 (such as amicroprocessor) which controls the overall operation of the electronicdevice 300. The processing unit 302 is coupled to a plurality ofcomponents via a communication bus (not shown) which provides acommunication path between the components and the processing unit 302.

The electronic device 300 includes one or more output devices 304coupled to the processor 302. The one or more output devices 304 mayinclude, for example, a speaker and a display (e.g., a touchscreen).Generally, the output device(s) 304 of the electronic device 300 maycapable of providing visual output and/or other types of output (e.g.,audio, tactile or haptic output). The electronic device 300 may alsoinclude one or more additional input devices 306 coupled to theprocessor 302. The one or more input devices 306 may include, forexample, buttons, switches, dials, a keyboard or keypad, or navigationtool, depending on the type of electronic device 300. In some examples,an output device 304 (e.g., a touchscreen) may also serve as an inputdevice 306. A visual interface, such as a GUI, may be rendered anddisplayed on the touchscreen by the processor 302. A user may interactwith the GUI using the touchscreen and optionally other input devices(e.g., buttons, dials) to display relevant information, such as bankingor other financial information, etc. The electronic device 300 may alsoinclude a data port (not shown) such as a serial data port (e.g., USBdata port).

The electronic device 300 may also include one or more sensors (notshown) coupled to the processor 302. The sensors may include a biometricsensor, a motion sensor, a camera, an IR sensor, a proximity sensor, adata usage analyser, and possibly other sensors such as a satellitereceiver for receiving satellite signals from a satellite network,orientation sensor, electronic compass or altimeter.

The processor 302 is coupled to a communication interface 308, which mayinclude one or more transmitter(s), receiver(s) and/or transceiver(s)for exchanging radio frequency signals with a wireless network that ispart of the communication network. For example, the communicationinterface 308 may include one or a combination of Bluetooth transceiveror other short-range wireless transceiver, a Wi-Fi or other WLANtransceiver for communicating with a WLAN via a WLAN access point (AP),or a cellular transceiver for communicating with a radio access network(e.g., cellular network).

In some examples, the electronic device 300 may also include a satellitereceiver (not shown) for receiving satellite signals from a satellitenetwork that comprises a plurality of satellites which are part of aglobal or regional satellite navigation system.

The processor 302 is also coupled to one or more memories 310, such asRAM, ROM or persistent (non-volatile) memory such as flash memory. Thememory(ies) 310 may store operating system software 312 executable bythe processor 302. One or more applications 314 executable by theprocessor 302 may also be stored in the memory(ies) 310. For example,the memory(ies) 310 may store instructions for implementing a visualinterface (e.g., a GUI). The memory(ies) 310 also may store a variety ofdata 316. The data 316 may include user data including user preferences,settings and possibly biometric data about the user for authenticationand/or identification; a download cache including data downloaded viathe communication interface 308; and saved files.

System software, software modules, specific device applications, orparts thereof, may be temporarily loaded into a volatile store, such asRAM, which is used for storing runtime data variables and other types ofdata or information. Communication signals received by the electronicdevice 300 may also be stored in RAM. Although specific functions aredescribed for various types of memory, this is merely one example, and adifferent assignment of functions to types of memory may be used inother embodiments.

The electronic device 300 may also include a power source (not shown),for example a battery such as one or more rechargeable batteries thatmay be charged, for example, through charging circuitry coupled to abattery interface such as a serial data port. The power source provideselectrical power to at least some of the components of the electronicdevice 300, and a battery interface may provide a mechanical and/orelectrical connection for the battery.

One or more functions/modules described as being provided at theelectronic device 300 may be implemented or provided by the applicationserver 200. For example, instructions for implementing a GUI may not bestored in the electronic device 300. Instead, the application server 200may store instructions for implementing a GUI.

FIGS. 4 and 5 are now described together. FIG. 4 illustrates an examplesignaling diagram of an example method 400 for creating a newmulti-applicant account profile. FIG. 5 is a flowchart illustrating amethod 500, which may be performed by the application server 200 as partof the method 400. Although FIG. 4 shows signals being transmitteddirectly between the entities illustrated, it should be understood thatthere may be one or more intermediate nodes (e.g., intermediate accesspoints and/or relay nodes) not shown for simplicity. Further, althoughFIG. 4 and FIG. 5 illustrate an order to the signals and steps of themethod 400, it should be understood that this is only for the purpose ofillustration; the method 400 may be performed in an order different fromthat specifically shown.

The method 400 may involve the application server 200, a first applicantdevice 110-1 (e.g., a client device 110 that is used by a firstapplicant to communicate with the application server 200), and one ormore second applicant devices 110-2 (e.g., one or more client devices110 that are used by a second applicant to communicate with theapplication server 200). Implementation of the method 400 may include asequence of interfaces, also referred to as user interfaces or graphicaluser interfaces (GUIs), which may be displayed at the first and/orsecond applicant device(s) 110-1, 110-2. Any such GUIs may be displayedat the applicant device(s) 110-1, 110-2 based on signals from theapplication server 200.

The first applicant device 110-1 transmits a signal 402 to theapplication server 200 requesting to apply for a new multi-applicantaccount. The request is made during a first session conducted betweenthe first applicant device 110-1 and the application server. It shouldbe noted that other interactions and tasks may be performed during thefirst session.

As part of the application for a new multi-applicant account, the firstapplicant device 110-1 transmits a signal 404 providing identificationinformation of the first applicant. The signal 404 is received at theapplication server 200 at step 502. This identification information maycontain private and/or sensitive information (e.g., the applicant'ssocial security number (SSN), birthdate, home address, etc.). Theidentification information may enable the application server 200 toverify the identity of the first applicant (e.g., using theauthentication server 130). In some examples, the identificationinformation may identify the first applicant as an existing customer ofthe institution (e.g., the identification information may be a customernumber or customer login). In such examples, the identificationinformation may enable the application server 200 to identify and/orretrieve the corresponding customer profile (which may contain furtheridentification information) from the customer database 144 in thebusiness services server 140.

The first applicant device 110-1 further transmits a signal 406providing contact information for a second applicant of themulti-applicant account. The signal 406 is received at the applicationserver 200 at step 504. The contact information includes two or morepieces of contact data for the second applicant. For example, thecontact information may include contact data enabling at least twodifferent modes for contacting the second applicant. Modes of contactthat use different communication networks may be considered differentmodes of contact. For example, contacting via email, text message,social media private message, physical letter, or telephone call may allbe considered different modes for contacting the second applicant. Thecontact information may include, for example, an email address and atelephone number for the second applicant. In other examples, thecontact information may enable the second applicant to be contactedusing only one mode of contact, but at different contact addresses. Forexample, the contact information may include a home telephone number anda business telephone number for the second applicant. Other suchvariations may be possible.

In some examples, two or more of the signals 402-406 may be transmittedtogether (e.g., submitted via a single online form with multiple inputfields). In other examples, the signals 402-406 may be transmittedseparately, such as in response to requests (not shown) from theapplication server 200.

The first session conducted between the first applicant device 110-1 andthe application server 200 may be ended after the application server 200has received all the requested identification information from the firstapplicant (and possibly any other information needed to create themulti-applicant account profile). Alternatively, the first session maycontinue and other transactions may be performed.

After receiving the contact information for the second applicant, theapplication server 200 transmits a signal 408 providing a one-timepassword to the second applicant device 110-2. The signal 408 istransmitted by the application server 200 at step 506. The one-timepassword is transmitted using one piece of contact data (e.g., an emailaddress) provided in the contact information.

The application server 200 also transmits a signal 410 providing aunique link to the same or different second applicant device 110-2. Thesignal 410 is transmitted by the application server 200 step 508. Theunique link is transmitted using a different piece of contact data(e.g., a telephone number) provided in the contact information.

The signals 408 and 410 may be received at the same second applicantdevice 110-2, via different modes of contact. For example, the secondapplicant device 110-2 may be capable of multiple modes of contact(e.g., may be a smartphone capable of receiving text messages and alsocapable of receiving email messages). The signals 408 and 410 may alsobe received at different second applicant devices 110-2, each receivingthe respective signal via a different mode of contact. For example, onesecond applicant device 110-2 (e.g., a cellular telephone) may becapable of receiving the one-time password in a text message; andanother second applicant device 110-2 (e.g., a desktop computer) may becapable of receiving the unique link in an email message. Other suchvariations may be possible.

In some examples, one of the signals 408 and 410 may be replaced by aphysical communication (e.g., a letter sent by post). For example, theapplication server 200 may generate a letter containing the one-timepassword or the unique link, and may cause the letter to be printed andmailed to a physical address (which may be included in the contactinformation) of the second applicant.

The one-time password and the unique link may be generated by theapplication server 200, and stored in a local database in associationwith each other. Any suitable method may be used by the applicationserver 200 to ensure uniqueness of the one-time password and the uniquelink. In some examples, the one-time password and the unique link mayautomatically expire after a predefined period of time (e.g., 24 hours),for greater security.

The unique link may be used to access a webpage (or other user portal)to which the one-time password is inputted. The entry of the one-timepassword, via the unique link, may be by the same second applicantdevice 110-2 that received the signal 408 or 410, or may be a differentsecond applicant device 110-2. The second applicant device 110-2transmits a signal 412, which requests a second session between thesecond applicant device 110-2 and the application server 200. The signal412 provides the one-time password together via the unique link.Typically, the second session is requested by and conducted with asingle second applicant device 110-2.

The application server 200, at 413, verifies (e.g., by comparison withinformation stored in a local database) that the correct one-timepassword has been provided via the unique link. After the correctone-time password has been received via the unique link, the applicationserver 200, at step 510, initiates the second session with the secondapplicant device 110-2. The use of two pieces of unique data (in thiscase, the one-time password and unique link), which are provided usingtwo different pieces of contact data, to verify the second applicant maybe considered a form of two-factor authentication.

The second session may be restricted to transactions related to creationof the multi-applicant account. For example, the second session mayautomatically cause the second applicant device 110-2 to display anonline form requesting identification information from the secondapplicant. In other examples, the second session may enable other typesof transactions and tasks to be performed. For example, the secondsession may, in addition to a request for identification information,also provide one or more options for performing other transactions andtasks (e.g., option to apply for a credit card, option to apply for amortgage, etc.) that are normally provided by the application server200.

During the second session, the second applicant device 110-2 transmits asignal 414 providing identification information about the secondapplicant. The signal 414 is received by the application server 200 atstep 512. This identification information may contain private and/orsensitive information (e.g., the applicant's social security number(SSN), birthdate, home address, etc.). The identification informationmay enable the application server 200 to verify the identity of thesecond applicant (e.g., using the authentication server 130). In someexamples, the identification information may identify the secondapplicant as an existing customer of the institution (e.g., theidentification information may be a customer number or customer login).In such examples, the identification information may enable theapplication server 200 to identify and/or retrieve the correspondingcustomer profile (which may contain further identification information)from the customer database 144 in the business services server 140.

After the identification information from the first applicant and theidentification information from the second applicant have been received,the application server 200, at step 514, verifies the identificationinformation of all the applicants. The application server 200 may, forexample, use the authentication server 130 to perform verification ofthe identification information. The authentication server 130 may send asignal to the application server 200 if the identification informationis authentic, thus enabling the application server 200 to verify theidentification information. In examples in which one or both applicantsare existing customers of the institution, verification ofidentification information may include confirming that the applicant(s)are existing customer(s). The application server 200 may use thebusiness services server 140 to confirm that the applicant(s) areexisting customer(s) (e.g., by determining whether the providedidentification information matches an existing customer profile storedin the customer database 144), and the application server 200 mayretrieve further identification information from the customer database144 of the business services server 140.

If verification of identification information for one or both applicantsfails, the application server 200 may generate a notification to therespective applicant(s) indicating that verification failed. Thenotification may provide an opportunity to re-enter identificationinformation. After verification fails for a predefined number of times(e.g., five times), the application server 200 may generate anotification to all applicants indicating that the request to create anew multi-applicant account has been refused.

After the identification information has been verified, the applicationserver 200, at step 516, creates a new multi-applicant account profile.The application server 200 may also instruct the business servicesserver 140 to create a new customer profile for any applicant that isnot an existing customer. The newly created multi-applicant accountprofile is linked to the customer profiles of the first and secondapplicants.

For simplicity, steps 514 and 516 are represented by a single block 416.

Optionally, at step 518, the application server 200 may transmit signals418 to one or both applicants to notify that the multi-applicant accountwas successfully created. The notification may include information aboutthe account, such as the account number.

The signals and steps illustrated in the drawings are shown in anexample order, which is not intended to be limiting. It should beunderstood that the order of the signals and steps may be varied. Forexample, the identification information of the first applicant may beprovided at any time during the first session, and may be provided laterthan the identification information of the second applicant, forexample. In other words, the initiation of the second session andcompletion of identification information for the second applicant is notnecessarily reliant on completion of identification information for thefirst applicant. In this way, the second applicant does not need to waiton the first applicant.

It should be noted that the first and second sessions may overlap intime. For example, the second applicant may providing identificationinformation during the second session at the same time that the firstapplicant is still providing identification information during the firstsession.

It should also be noted that the first session and the second sessionmay be independent from each other. The first applicant may not have anyknowledge of any information exchanged in the second session; and thesecond applicant may not have any knowledge of any information exchangedin the first session. The first applicant may not be able to navigate tothe webpage being used by the second applicant, and vice versa. Theidentification information provided in one session may be inaccessiblevia another session. Thus, the privacy of each applicant may bemaintained.

FIGS. 4 and 5 show creation of a multi-applicant account having twoapplicants. It should be understood that similar methods may be used forcreation of a multi-applicant account having three or more applicants.For example, during the first session, contact information one or moreadditional applicants may be provided. At least two different pieces ofcontact data are provided for each additional applicant. After the firstapplicant provides contact information for each additional applicant, aunique pair of one-time password and unique link is generated andprovided to each additional applicant. Each applicant then may request arespective session with the application server, using the respectivepair of one-time password and unique link. Each session conducted witheach applicant may be independent from each other session, to helpmaintain privacy between applicants. Any of the sessions may beconducted in any appropriate temporal order.

FIGS. 6A-6E illustrate some example user interfaces that may bedisplayed during the method 400. There may be other user interfaces, inaddition to or instead of those shown, that may be provided during themethod 400. The application server 200 may provide signals to a clientdevice (e.g., first or second applicant device 110-1, 110-2) to displayone or more of the example user interfaces illustrated in FIGS. 6A-6E.

In some examples, one or more user interfaces may provide an onlineform, with appropriate input fields, to enable an applicant to providethe required information (and possibly also optional information) tocreate the requested multi-applicant account profile. Where appropriate,the example user interfaces may also enable an applicant to provide therequired information (and possibly also optional information) to createa new customer profile for that applicant. The example user interfacesmay be designed to be similar to an online form for creating a singleapplicant account profile, to user convenience.

In examples where an applicant has been identified as an existingcustomer of the institution (e.g., the applicant has provided a loginname and a valid password corresponding to an existing customerprofile), one or more fields of the online form may be automaticallyfilled in by the application server 200, using information retrievedfrom the customer profile.

In other examples, an applicant may interact with the application server200 in other ways, for example via text messaging (e.g., using achatbot), instead of using an online form to provide the requiredinformation (and possibly also optional information).

FIGS. 6A-6E are now described in detail, with references made to FIG. 4where applicable.

FIG. 6A shows an example user interface 610 that may be used to enablethe first applicant, during the first session, to provide contactinformation for the second applicant. The application server 200 maytransmit signals to the first applicant device 110-1 to cause the userinterface 610 to be displayed on the first applicant device 110-1. Inthis example, the user interface 610 provides a field 612 to input thename of the second applicant. The user interface 610 also enables inputof two pieces of contact data for the second applicant. In this example,a drop-down menu 614 a and input field 614 b enables input of a firstpiece of contact data, and another drop-down menu 616 a and anotherinput field 616 b enables input of a second piece of contact data. Eachdrop-down menu 614 a, 616 a may provide options for selecting a mode ofcontact (e.g., email, phone, text, etc.). In some examples, after onemode of contact has been selected in one of the drop-down menus 614 a,616 a, that mode of contact may be grayed-out or otherwise unavailableto be selected in the other drop-down menu 616 a, 614 a; this may be toensure that the two pieces of contact data provided for the secondapplicant are for two different modes of contact.

The user interface 610 also provides a selectable option 618 to add athird (or more) applicant. If the option 618 is selected, the userinterface 610 may be expanded to display additional input fields forinputting name and contact information for the third (or more)applicant. Selection of a submit button 619 results in the contactinformation of the second applicant being transmitted to the applicationserver 200 (e.g., signal 406 in FIG. 4 ).

The application server 200 may use the contact information of the secondapplicant to communicate with the second applicant device(s) 110-2, tocause the example user interfaces 620 an 630 (FIGS. 6B and 6C) to bedisplayed on the respective second applicant device(s) 110-2.

For example, the signal 408 may cause the example user interface 620 tobe displayed (e.g., in a text message) on a text message-capable secondapplicant device 110-2, to provide the unique one-time password 622. Thesignal 410 may cause the example user interface 630 to be displayed(e.g., in an email) on an email-capable second applicant device 110-2,to provide the unique link 632.

After the second applicant accesses the unique link (e.g., by clickingon the link 632 in the user interface 630), the second applicant device110-2 may navigate to the webpage referenced by the unique link, and theuser interface 640 of FIG. 6D may be presented. The example userinterface 640 provides an input field 642 to input the one-time password622. Selection of the submit button 644 results in the one-timepassword, inputted via the unique link, to be transmitted to theapplication server 200 (e.g., signal 412 in FIG. 4 ).

FIG. 6E shows an example user interface 650 that may be used to enablethe second applicant, during the second session, to provideidentification information. The application server 200 may transmitsignals to the second applicant device 110-2 to cause the user interface650 to be displayed on the second applicant device 110-2. In thisexample, the user interface 650 provides fields 652, 654, 656 to inputthe full legal name, birthdate and home address, respectively, of thesecond applicant. Selection of a submit button 658 results in theidentification information of the second applicant being transmitted tothe application server 200 (e.g., signal 414 in FIG. 4 ).

In some examples, the user interface presented for the second applicantto input identification information may be similar to a user interfacethat is presented for the first applicant to input identificationinformation. However, in some examples, the first applicant may beprovided with additional options (e.g., option to add a third or moreapplicant, or option to select the type of joint account) not availableto the second applicant.

In some examples, the second applicant may be enabled to add a thirdapplicant. Such an example is described below.

FIGS. 7 and 8 are now described together. FIG. 7 illustrates an examplesignaling diagram of another example method 700 for creating a newmulti-applicant account profile. FIG. 8 is a flowchart illustrating amethod 800, which may be performed by the application server 200 as partof the method 700. Although FIG. 7 shows signals being transmitteddirectly between the entities illustrated, it should be understood thatthere may be one or more intermediate nodes (e.g., intermediate accesspoints and/or relay nodes) not shown for simplicity. Further, althoughFIG. 7 and FIG. 8 illustrate an order to the signals and steps of themethod 700, it should be understood that this is only for the purpose ofillustration; the method 700 may be performed in an order different fromthat specifically shown.

The method 700 may be similar to the method 400 in some ways. Whereappropriate, the same reference numerals have been used to indicatesimilar signals or steps. The method 700 enables creation of a newmulti-applicant account profile, and enables the second applicant tofurther add a third applicant. In this example, each additionalapplicant may further invite another applicant. Thus, in this example,the ability to add applicants to the multi-applicant account is notlimited to the first applicant.

Similar to the method 400, the method 700 includes signals 402-406transmitted from the first applicant device 110-1 to the applicationserver 200, signals 408-410 transmitted from the application server 200to the second applicant device(s) 110-2, and signals 412-414 transmittedfrom the second applicant device 110-2 to the application server 200.From the application server 200 viewpoint, steps 510-512 are similar tothose described above for the method 400.

During the second session conducted between the second applicant device110-2, the second applicant device 110-2 transmits a signal 422providing contact information for a third applicant. At the applicationserver 200, the signal 422 is received at step 520. Similarly to thecontact information provided for the second applicant, the contactinformation for the third applicant includes two or more pieces ofcontact data for the third applicant. For example, the contactinformation may include contact data enabling at least two differentmodes for contacting the third applicant. In other examples, the contactinformation may enable the third applicant to be contacted using onlyone mode of contact, but at different contact addresses. Other suchvariations may be possible.

In some examples, the signals 414 and 422 may be transmitted together(e.g., submitted via a single online form with multiple input fields).In other examples, the signals 414 and 422 may be transmittedseparately, such as in response to requests (not shown) from theapplication server 200.

Optionally, the application server 200 may, at step 522, transmit asignal 424 to notify the first applicant device 110-1 that the thirdapplicant was added by the second applicant. The notification may askthe first applicant to confirm or approve the addition of the thirdapplicant. If the first applicant does not confirm or approve theaddition of the third applicant, the addition of the third applicant maybe refused by the application server 200.

After the contact information for this third applicant has been received(and after receipt of confirmation or approval from the first applicant,if requested), the application server 200 transmits a signal 426providing a one-time password to the third applicant device 110-3. Thesignal 426 is transmitted by the application server 200 at step 524. Theone-time password is transmitted using one piece of contact data (e.g.,an email address) provided in the contact information.

The application server 200 also transmits a signal 428 providing aunique link to the same or different third applicant device 110-3. Thesignal 428 is transmitted by the application server 200 step 526. Theunique link is transmitted using a different piece of contact data(e.g., a telephone number) provided in the contact information.

The signals 426 and 428 may be received at the same third applicantdevice 110-3, via different modes of contact. The signals 426 and 428may also be received at different third applicant devices 110-3, eachreceiving the respective signal via a different mode of contact.

In some examples, one of the signals 426 and 428 may be replaced by aphysical communication (e.g., a letter sent by post). For example, theapplication server 200 may generate a letter containing the one-timepassword or the unique link, and may cause the letter to be printed andmailed to a physical address (which may be included in the contactinformation) of the third applicant.

The unique link may be used to access a webpage to which the one-timepassword is inputted. The entry of the one-time password, via the uniquelink, may be by the same third applicant device 110-3 that received thesignal 426 or 428, or may be a different third applicant device 110-3.The third applicant device 110-3 transmits a signal 430, which requestsa third session between the third applicant device 110-3 and theapplication server 200. The signal 430 provides the one-time passwordtogether via the unique link. Typically, the third session is requestedby and conducted with a single third applicant device 110-3.

The application server 200, at 431, verifies (e.g., by comparison withinformation stored in a local database) that the correct one-timepassword has been provided via the unique link. After the correctone-time password has been received via the unique link, the applicationserver 200, at step 528, initiates the third session with the thirdapplicant device 110-3.

The third session may be restricted to transactions related to creationof the multi-applicant account. In other examples, the third session mayenable other types of transactions and tasks to be performed.

During the third session, the third applicant device 110-3 transmits asignal 432 providing identification information about the thirdapplicant. The signal 432 is received by the application server 200 atstep 530. This identification information may contain private and/orsensitive information (e.g., the applicant's social security number(SSN), birthdate, home address, etc.). The identification informationmay enable the application server 200 to verify the identity of thethird applicant (e.g., using the authentication server 130). In someexamples, the identification information may identify the thirdapplicant as an existing customer of the institution (e.g., theidentification information may be a customer number or customer login).In such examples, the identification information may enable theapplication server 200 to identify and/or retrieve the correspondingcustomer profile (which may contain further identification information)from the customer database 144 in the business services server 140.

The method 700 then proceeds with verification of identificationinformation and creation of the multi-applicant account profile (andoptionally notifying applicants that account was successfully created),similar to that described above with reference to FIGS. 4 and 5 .

FIGS. 9A-9C illustrate some example user interfaces that may bedisplayed during the method 700. There may be other user interfaces, inaddition to or instead of those shown, that may be provided during themethod 700. The application server 200 may provide signals to a clientdevice (e.g., first or second applicant device 110-1, 110-2) to displayone or more of the example user interfaces illustrated in FIGS. 9A-9C.One or more of the user interfaces discussed above with respect to FIGS.6A-6D may be used together with the user interfaces illustrated in FIGS.9A-9C. The use of the previously-described user interfaces of FIGS.6A-6D will not be discussed in detail in the context of the method 700.

FIGS. 9A-9C are now described in detail, with references made to FIG. 7where applicable.

FIG. 9A shows an example user interface 910 that may be used to enablethe second applicant, during the second session, to provideidentification information. The user interface 910 may be used insteadof the previously-described user interface 650 of FIG. 6E. Theapplication server 200 may transmit signals to the second applicantdevice 110-2 to cause the user interface 910 to be displayed on thesecond applicant device 110-2. In this example, the user interface 910provides fields 912, 914, 916 to input the full legal name, birthdateand home address, respectively, of the second applicant, similarly tothe user interface 650 of FIG. 6E.

In addition, the user interface 910 also provides a selectable option918 to add a third (or more) applicant. If the option 918 is selected,the user interface 910 may be expanded to display additional inputfields (e.g., similar to the input fields discussed above with respectto the user interface 610 of FIG. 6A) for inputting name and contactinformation for the third (or more) applicant. In some examples, insteadof expanding the user interface 910 to display input fields forinputting contact information for the third (or more) applicant, aseparate user interface (not shown) may be displayed. Selection of asubmit button 919 results in the identification information of thesecond applicant, as well as the contact information of the third (ormore) applicant, being transmitted to the application server 200 (e.g.,signals 414 and 422 in FIG. 4 ).

Optionally, the application server 200 may transmit the signal 424 tonotify the first applicant that the third (or more) applicant was addedby the second applicant. FIG. 9B shows an example user interface 920that may be caused to be displayed on the first applicant device 110-1,to provide this notification. The user interface 920 in this exampleincludes a link 922 that may be selected by the first applicant in orderto confirm or approve the addition of the third (or more applicant) bythe second applicant. In other examples, the user interface 920 may notinclude the link 922 and may only serve to notify the first applicant,without providing any option to confirm or approve the addition of thethird (or more) applicant.

In this example, selection of the link 922 may cause the first applicantdevice 110-1 to navigate to a webpage where the user interface 930 ofFIG. 9C may be presented. The user interface 930 may provide information932 identifying the third (or more) applicant that was added (e.g.,providing the name of the third (or more) applicant) and possibly alsoidentifying the second applicant who added the third (or moreapplicant). The example user interface 930 may include a selectableoption 934 to confirm or approve the addition of the third (or more)applicant for the multi-applicant account, and may also include aselectable option 936 to deny or refuse the addition of the third (ormore) applicant.

If the third (or more) applicant is confirmed or approved by the firstapplicant, the application server 200 may use the contact information ofthe third applicant to communicate with the third applicant device(s)110-3, to provide the one-time password and unique link to the thirdapplicant, as discussed previously.

In some examples, the present disclosure enables creation ofmulti-applicant account profiles remotely (e.g., via online sessions) bythe applicants. Multiple sessions, each conducted by a respectivedifferent applicant, may be conducted in order for the requiredinformation (e.g., identification information from each applicant) to bereceived. Each session may be independent of each other session,accessed using a unique pair of one-time password and unique link. Fromthe viewpoint of each applicant, their portion of the application iscomplete after submission of the required information (e.g., their ownidentification information) has been completed during their own session.The information gathered from the separate sessions is separatelycollected and collated by the application server to complete a singleapplication for the multi-applicant account. The use of multiplesessions may provide greater flexibility and convenience, because eachapplicant may conduct their own session at their own time and location.

In some examples, each applicant's session may be private from eachother applicant. The information provided by an applicant during theirsession may be inaccessible to each other applicant (and inaccessible toeven the first applicant who initiated the application for themulti-applicant account). This may help to ensure privacy of eachapplicant, by shielding private identification information from otherapplicants.

In some examples, the present disclosure may be used for openingbusiness accounts, such as for multi-owner businesses or partnerships.

Although the present disclosure is described, at least in part, in termsof methods, a person of ordinary skill in the art will understand thatthe present disclosure is also directed to the various components forperforming at least some of the aspects and features of the describedmethods, be it by way of hardware (digital signal processors (DSPs),application specific integrated circuits (ASICs), or field-programmablegate arrays (FPGAs)), software or a combination thereof. Accordingly,the technical solution of the present disclosure may be embodied in anon-volatile or non-transitory machine-readable medium (e.g., opticaldisk, flash memory, etc.) having stored thereon executable instructionstangibly stored thereon that enable a processing device (e.g., a datamanager) to execute examples of the methods disclosed herein.

The steps and/or operations in the flowcharts and drawings describedherein are for purposes of example only. There may be many variations tothese steps and/or operations without departing from the teachings ofthe present disclosure. For instance, the steps may be performed in adiffering order, or steps may be added, deleted, or modified.

The coding of software for carrying out the above-described methodsdescribed is within the scope of a person of ordinary skill in the arthaving regard to the present disclosure. Machine-readable codeexecutable by one or more processors of one or more respective devicesto perform the above-described method may be stored in amachine-readable medium such as the memory of the data manager. Theterms “software” and “firmware” are interchangeable within the presentdisclosure and comprise any computer program stored in memory forexecution by a processor, comprising RAM memory, ROM memory, erasableprogrammable ROM (EPROM) memory, electrically EPROM (EEPROM) memory, andnon-volatile RAM (NVRAM) memory. The above memory types are examplesonly and are thus not limiting as to the types of memory usable forstorage of a computer program.

All values and sub-ranges within disclosed ranges are also disclosed.Also, although the systems, devices and processes disclosed and shownherein may comprise a specific plurality of elements/components, thesystems, devices and assemblies may be modified to comprise additionalor fewer of such elements/components. For example, although any of theelements/components disclosed may be referenced as being singular, theembodiments disclosed herein may be modified to comprise a plurality ofsuch elements/components. The subject matter described herein intends tocover and embrace all suitable changes in technology.

The term “processor” may comprise any programmable system comprisingsystems using micro- or nano-processors/controllers, reduced instructionset circuits (RISC), ASICs, logic circuits, and any other circuit orprocessor capable of executing the functions described herein. The term“database” may refer to either a body of data, a relational databasemanagement system (RDBMS), or to both. As used herein, a database maycomprise any collection of data comprising hierarchical databases,relational databases, flat file databases, object-relational databases,object-oriented databases, and any other structured collection ofprofiles, records or data that is stored in a computer system. The aboveexamples are example only, and thus are not intended to limit in any waythe definition and/or meaning of the terms “processor” or “database”.

The present disclosure includes figures showing designs having boundarylines illustrated as solid lines. The present disclosure is not limitedto design drawings that strictly include all solid boundary lines.Designs disclosed herein include design drawings in which one or moreboundary lines shown as solid lines may be disclaimed from the drawing.Boundary lines that are depicted in the presently disclosed drawings assolid lines may be replaced with broken boundary lines, and vice versa.

The present disclosure may be embodied in other specific forms withoutdeparting from the subject matter of the claims. The described exampleembodiments are to be considered in all respects as being onlyillustrative and not restrictive. The present disclosure intends tocover and embrace all suitable changes in technology. The scope of thepresent disclosure is, therefore, described by the appended claimsrather than by the foregoing description. The scope of the claims shouldnot be limited by the embodiments set forth in the examples, but shouldbe given the broadest interpretation consistent with the description asa whole.

The invention claimed is:
 1. A server comprising: at least onecommunication interface for communication with one or more clientdevices; a processor coupled to the communication interface; and amemory coupled to the processor, the memory having computer-executableinstructions stored thereon, the instructions, when executed by theprocessor, cause the server to: during a first remote session, receive,via the communication interface, a signal representing a request toapply for a new multi-applicant account, a signal representingidentification information for verifying an identity of a firstapplicant, and a signal representing at least two pieces of contact datafor a second applicant provided by the first applicant; in response toreceiving the signal representing the at least two pieces of contactdata for the second applicant: transmit, using a first piece of contactdata from the at least two pieces of contact data for the secondapplicant, via the communication interface, a signal representing aunique link; and transmit, using a second piece of contact data from theat least two pieces of contact data for the second applicant, via thecommunication interface, a signal representing a one-time password;initiate a second remote session, in response to receipt, via thecommunication interface, of the signal representing the one-timepassword, the one-time password being provided via the unique link;during the second remote session, receive, via the communicationinterface, a signal representing identification information forverifying an identity of the second applicant; and create a newmulti-applicant account profile, after verifying the identity of thefirst applicant and the identity of the second applicant using theidentification information of the first applicant and the identificationinformation of the second applicant respectively.
 2. The server of claim1, wherein the instructions, when executed by the processor, furthercause the server to: during the first remote session, receive, via thecommunication interface, a signal representing at least two pieces ofcontact data for a third applicant; transmit, using a first piece ofcontact data for the third applicant, via the communication interface, asignal representing another unique link; transmit, using a second pieceof contact data for the third applicant, via the communicationinterface, a signal representing another one-time password; initiate athird remote session, in response to receipt, via the communicationinterface, of a signal representing the other one-time password, theother one-time password being provided via the other unique link; andduring the third remote session, receive, via the communicationinterface, a signal representing identification information forverifying an identity of the third applicant; wherein the newmulti-applicant account profile is created after verifying the identityof the first applicant, the identity of the second applicant and theidentity of the third applicant using the identification information ofthe first applicant, the identification information of the secondapplicant, and the identification information of the third applicantrespectively.
 3. The server of claim 2, wherein the second remotesession and the third remote session can be conducted in parallel, or inany temporal order.
 4. The server of claim 1, wherein the instructions,when executed by the processor, further cause the server to: during thesecond remote session, receive, via the communication interface, asignal representing at least two pieces of contact data for a thirdapplicant; transmit, using a first piece of contact data for the thirdapplicant, via the communication interface, a signal representinganother unique link; transmit, using a second piece of contact data forthe third applicant, via the communication interface, a signalrepresenting another one-time password; initiate a third remote session,in response to receipt, via the communication interface, of a signalrepresenting the other one-time password, the other one-time passwordbeing provided via the other unique link; and during the third remotesession, receive, via the communication interface, a signal representingidentification information of the third applicant; wherein the newmulti-applicant account profile is created after verifying the identityof the first applicant, the identity of the second applicant and theidentity of the third applicant using the identification information ofthe first applicant, the identification information of the secondapplicant, and the identification information of the third applicantrespectively.
 5. The server of claim 4, wherein the instructions, whenexecuted by the processor, further cause the server to: transmit, viathe communication interface, signals representing a notification to thefirst applicant indicating addition of the third applicant; wherein thenew multi-applicant account profile is created after receiving, via thecommunication interface, signals representing confirmation of the thirdapplicant by the first applicant.
 6. The server of claim 1, wherein theat least two pieces of contact data for the second applicant include atleast two of: an email address; a phone number; or a social mediaaccount.
 7. The server of claim 6, wherein the signal representing theunique link is transmitted using one of: an email message to the emailaddress; a text message to the phone number; or a private message to thesocial media account; and wherein the signal representing the one-timepassword is transmitted using a different one of: an email message tothe email address; a text message to the phone number; or a privatemessage to the social media account.
 8. The server of claim 1, whereinthe instructions, when executed by the processor, further cause theserver to: receive the identification information from one of the firstapplicant or the second applicant by: verifying that the one of thefirst applicant or the second applicant is an existing customer; andretrieving the identification information of the one of the firstapplicant or the second applicant from a customer database.
 9. Theserver of claim 1, wherein the instructions, when executed by theprocessor, further cause the server to: after creating themulti-applicant account, transmit, via the communication interface,signals representing a respective notification to each applicant toindicate the multi-applicant account was successfully created.
 10. Theserver of claim 1, wherein the identification information of the secondapplicant is inaccessible to the first applicant, and the identificationinformation of the first applicant is inaccessible to the secondapplicant.
 11. A method at a server, the method comprising: during afirst remote session, receiving a signal representing a request to applyfor a new multi-applicant account, a signal representing identificationinformation for verifying an identity of a first applicant, and a signalrepresenting at least two pieces of contact data for a second applicantprovided by the first application; in response to receiving the signalrepresenting the at least two pieces of contact data for the secondapplicant: transmitting, using a first piece of contact data from the atleast two pieces of contact data for the second applicant a signalrepresenting a unique link; and transmitting, using a second piece ofcontact data from the at least two pieces of contact data for the secondapplicant, a signal representing a one-time password; initiating asecond remote session, in response to receipt of the signal representingthe one-time password, the one-time password being provided via theunique link; during the second remote session, receiving a signalrepresenting identification information for verifying an identity of thesecond applicant; and creating a new multi-applicant account profile,after verifying the identity of the first applicant and the identity ofthe second applicant using the identification information of the firstapplicant and the identification information of the second applicantrespectively.
 12. The method of claim 11, further comprising: during thefirst remote session, receiving a signal representing at least twopieces of contact data for a third applicant; transmitting, using afirst piece of contact data for the third applicant a signalrepresenting another unique link; transmitting, using a second piece ofcontact data for the third applicant a signal representing anotherone-time password; initiating a third remote session, in response toreceipt of a signal representing the other one-time password, the otherone-time password being provided via the other unique link; and duringthe third remote session, receiving a signal representing identificationinformation for verifying an identity of the third applicant; whereinthe new multi-applicant account profile is created after verifying theidentity of the first applicant, the identity of the second applicantand the identity of the third applicant using the identificationinformation of the first applicant, the identification information ofthe second applicant, and the identification information of the thirdapplicant respectively.
 13. The method of claim 12, wherein the secondremote session and the third remote session can be conducted inparallel, or in any temporal order.
 14. The method of claim 11, furthercomprising: during the second remote session, receiving a signalrepresenting at least two pieces of contact data for a third applicant;transmitting, using a first piece of contact data for the thirdapplicant a signal representing another unique link; transmitting, usinga second piece of contact data for the third applicant a signalrepresenting another one-time password; initiating a third remotesession, in response to receipt of a signal representing the otherone-time password, the other one-time password being provided via theother unique link; and during the third remote session, receiving asignal representing identification information of the third applicant;wherein the new multi-applicant account profile is created afterverifying the identity of the first applicant, the identity of thesecond applicant and the identity of the third applicant using theidentification information of the first applicant, the identificationinformation of the second applicant, and the identification informationof the third applicant respectively.
 15. The method of claim 14, furthercomprising: transmitting signals representing a notification to thefirst applicant indicating addition of the third applicant; wherein thenew multi-applicant account profile is created after receiving signalsrepresenting confirmation of the third applicant by the first applicant.16. The method of claim 11, wherein the at least two pieces of contactdata for the second applicant include at least two of: an email address;a phone number; or a social media account; wherein the signalrepresenting the unique link is transmitted using one of: an emailmessage to the email address; a text message to the phone number; or aprivate message to the social media account; and wherein the signalrepresenting the one-time password is transmitted using a different oneof: an email message to the email address; a text message to the phonenumber; or a private message to the social media account.
 17. The methodof claim 11, wherein receiving the identification information from oneof the first applicant or the second applicant comprises: verifying thatthe one of the first applicant or the second applicant is an existingcustomer; and retrieving the identification information of the one ofthe first applicant or the second applicant from a customer database.18. The method of claim 11, wherein the identification information ofthe second applicant is inaccessible to the first applicant, and theidentification information of the first applicant is inaccessible to thesecond applicant.
 19. A non-transitory machine-readable medium havingtangibly stored thereon executable instructions for execution by aprocessor of a server, wherein the instructions, when executed by theprocessor, cause the server to: during a first remote session, receive,via a communication interface of the server, a signal representing arequest to apply for a new multi-applicant account, a signalrepresenting identification information for verifying an identity of afirst applicant, and a signal representing at least two pieces ofcontact data for a second applicant from the first application; inresponse to receiving the signal representing the at least two pieces ofcontact data for the second applicant: transmit, using a first piece ofcontact data from the at least two pieces of contact data for the secondapplicant, via the communication interface, a signal representing aunique link; and transmit, using a second piece of contact data from theat least two pieces of contact data for the second applicant, via thecommunication interface, a signal representing a one-time password;initiate a second remote session, in response to receipt, via thecommunication interface, of the signal representing the one-timepassword, the one-time password being provided via the unique link;during the second remote session, receive, via the communicationinterface, a signal representing identification information forverifying an identity of the second applicant; and create a newmulti-applicant account profile, after verifying the identity of thefirst applicant and the identity of the second applicant using theidentification information of the first applicant and the identificationinformation of the second applicant respectively.
 20. The server ofclaim 1, wherein the instructions, when executed by the processor,further cause the server to: during the first remote session, receivethe signal representing the at least two pieces of contact data for thesecond applicant provided by the first applicant, the at least twopieces of contact data enabling at least two different modes ofcontacting the second applicant; and in response to receiving the signalrepresenting the at least two pieces of contact data for the secondapplicant: transmit, using the first piece of the contact data via afirst mode of contact, the signal representing the unique link; andtransmit, using the second piece of the contact data via a second modeof contact, the signal representing the one-time password.